Release 2.4.0 : Improve WordPress site support in slic here - #247
Open
defunctl wants to merge 2 commits into
Open
Release 2.4.0 : Improve WordPress site support in slic here#247defunctl wants to merge 2 commits into
slic here#247defunctl wants to merge 2 commits into
Conversation
shvlv
reviewed
Aug 7, 2026
shvlv
left a comment
There was a problem hiding this comment.
I tried locally and got the following error for plugin that works good with 2.3.0:
In WPLoader.php line 507:
lucatume\WPBrowser\Module\WPLoader module is not configured!
The WordPress installation is already configured.
In Scaffolded.php line 43:
The WordPress installation is already configured.
Do we have a migration guide?
Contributor
Author
Thanks for testing. We shouldn't need a guide. Which plugin so I can test and see what's going on? Edit: it asked you to upgrade and download the new containers right? |
yes |
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The main reason for these changes is to make
slic herework properly with actual WordPress site repositories.Previously slic assumed WordPress lived directly in the mounted directory and that content always lived in
wp-content/. This doesn't work very well for projects that install WordPress inwp/, usecontent/, or need the full project available inside the container.Main Changes
slic herenow mounts the entire WordPress project into/var/www/html, including projects that install WordPress inwp/.content/orwp-content/./var/www/html/wp-content.wp-content/directory when a project usescontent/due to docker mounts.2.4.0.release/x.x.xbranches and GitHub Releases.Previously slic would actually delete the project's
object-cache.phpbefore running tests. This is especially dangerous with site mode because that can be a real file in the repository.The object cache drop-in is now disabled inside the containers using a PHP prepend file. This leaves the host project's file completely untouched.
Testing
I tested this using the
software.liquidweb.comproject, which has WordPress installed inwp/and usescontent/instead ofwp-content/. I also tested on another of other projects/plugins./var/www/html./var/www/html/content.object-cache.phpis not changed or removed.object-cache.phpwhen one does not exist.slicand verify this would not break on those.I used this branch/images here: https://github.com/stellarwp/software.liquidweb.com/actions/runs/31132177214/job/92723444428?pr=326